Understanding the Hypertrieve database engine


	BlueCielo Meridian Enterprise 2013 Administrator's Guide \| BlueCielo ECM Solutions

You are here: BlueCielo Meridian Enterprise Administrator's Guide > Creating and maintaining vaults > Understanding the Hypertrieve database engine

Understanding the Hypertrieve database engine

The Hypertrieve database engine is a highly efficient, object-oriented database that is developed by BlueCielo ECM Solutions and embedded into Meridian Enterprise. It is optimized for use with Meridian and provided so that Meridian customers can implement engineering content management system without the need for additional software.

Notes

To migrate an existing vault from one generation of database engine to another, you must restore a backup of the source vault after first setting the destination database engine name in the DLLName setting in the vault's DataStore.ini file. The general procedure for restoring a vault is described in Moving a Hypertrieve vault.

Hypertrieve requires very little system administration and, in fact, has no database management user interface. The data files for a vault stored in Hypertrieve reside in the location specified when the vault was created, C:\BC-Meridian Vaults by default. Each of the Hypertrieve files are named <VaultName>.* where each file extension is described in the following table.

Hypertrieve database engine file types
File Extension	Description
.csv	Progress information for a stopped batch import so that the import may be resumed at a later time.
.hdb	Main data file. This file is always open when the EDM Server service is running.
.lck	Database lock file. This file is always present when the .hdb file is open by the EDM Server service.
.log	Transaction log file. This file accumulates document property changes until one of these events occurs: The log file reaches the size specified by the Maximum log size option A Prepare for Backup operation is executed The EDM Server service is stopped When one of these events occurs, the contents of the log file are committed to the .hdb file, a new snapshot is generated and an empty log file is initialized.
.snp	The last snapshot file created either by the Minimum snapshot interval option or a Prepare for Backup operation.